<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
    <meta name="copyright" content="2008-2011 Andreas Huber Dönni. Distributed under the Microsoft Public License (Ms-PL)." />
    <meta http-equiv="Content-Type" content="application/xhtml+xml; charset=utf-8" />
    <title>Manual</title>
</head>
<body>
    <h1>
        Manual</h1>
    <p>
        First of all, thank you for using Mews! Your feedback is important to me. To report
        issues and suggest new features, please use the issue tracker:</p>
    <p>
        http://mews.codeplex.com/workitem/list/basic</p>
    <p>
        For questions please use discussions:</p>
    <p>
        http://mews.codeplex.com/discussions</p>
    <p>
        <strong>Note</strong>: Neither of these pages work reliably with Internet Explorer
        Mobile.</p>
    <h2>
        Principles</h2>
    <ul>
        <li>Unlike many desktop NNTP readers, Mews is designed for offline use. That is, a network
            connection is only necessary while a Send/Receive operation is running.</li>
        <li>The application should behave mostly like Internet Explorer Mobile regarding connection
            management. Therefore, Mews automatically uses an existing network connection (e.g.
            when your device is already connected over Wi-Fi or cradled) and attempts to connect
            over cellular radio otherwise. The latter requires at least one modem connection
            entry under Start, Settings, Connections, Connections. A dial-up connection is closed
            automatically 30 seconds after a Send/Receive operation has finished. However, GPRS/3G
            connections are kept open because doing so neither costs anything nor consumes any
            additional battery power.</li>
        <li>The application can be fully controlled with the touch screen and mostly with hardware
            buttons (as far as Windows Mobile and your particular device allow).</li>
    </ul>
    <h2>
        Main Window</h2>
    <p>
        Depending on the mode, the main window is either a ...</p>
    <ul>
        <li>Blank Page</li>
        <li>Group Hierarchy View</li>
        <li>My Articles View</li>
    </ul>
    <h3>
        Group Hierarchy View</h3>
    <ul>
        <li>To display the article hierarchy of a group, tap <strong>Menu</strong>, <strong>
            Go To</strong>, <i>Group Display Name</i>.</li>
        <li>As in most other NNTP readers, articles are arranged in trees. Original articles
            appear leftmost, follow-up articles appear indented under the article they reply
            to. Original articles are sorted newest (top) to oldest (bottom).</li>
        <li>Threads can be expanded/collapsed by tapping the +/- icon. Pressing the right/left
            action button does the same with the currently selected article.</li>
        <li>Unread articles appear bold, watched articles appear red. Moreover, the icon of
            an article also shows whether the full article content is available: A torn icon
            appears when only header information has been received. If such an article is watched,
            a torn icon with an arrow indicates that the full article content will be received
            during the next Send/Receive operation.</li>
        <li>Tapping an article displays the article. Pressing the enter key (if your device
            has one) or the center action button does the same with the currently selected article.
        </li>
        <li>Tap &amp; hold on an article brings up the context menu. Holding the center action
            button does the same with the currently selected article. <strong>Watch All</strong>
            marks the selected article and all its follow-up articles as watched, <strong>Mark All
                as Read</strong> does the obvious.</li>
        <li>To write a new original article, tap <strong>Menu</strong>, <strong>New</strong>.</li>
        <li>To follow up to an article, tap <strong>Menu</strong>, <strong>Follow up</strong>
            while the article is displayed.</li>
    </ul>
    <h3>
        My Articles View</h3>
    <ul>
        <li>To display your articles, tap <strong>Menu</strong>, <strong>Go To</strong>, <strong>
            My Articles</strong>, <i>Folder</i>. <i>Folder</i> can refer to <strong>Draft</strong>,
            <strong>Outbox</strong>, <strong>Sent</strong> and <strong>Deleted</strong>, with
            the established meanings.</li>
        <li>Tapping an article displays the article. Pressing the enter key (if your device
            has one) or the center action button does the same with the currently selected article.</li>
        <li>Tap &amp; hold on an article brings up the context menu. Holding the center action
            button does the same with the currently selected article:
            <ul>
                <li><strong>Delete</strong> (available in the <strong>Draft</strong>, <strong>Outbox</strong>
                    and <strong>Sent</strong> folders) moves the currently selected article to the <strong>
                        Deleted</strong> folder.</li>
                <li><strong>Restore</strong> (available in the <strong>Deleted</strong> folder) moves
                    the currently selected article back to the original folder.</li>
            </ul>
        </li>
    </ul>
    <h3>
        Main Menu</h3>
    <ul>
        <li><strong>Send/Receive</strong> starts a background article send/receive operation.
            Irrespective of the mode, each such operation always receives the full content of
            all incomplete articles that are watched and all new articles that follow up to
            a watched article. All other new articles are received as follows:
            <ul>
                <li><strong>Minimal</strong> receives header information only. This mode is intended
                    for situations where the network connection has limited bandwith and/or is billed
                    by volume.</li>
                <li><strong>Full</strong> receives full article content. This mode is intended for cheap
                    high bandwith connections.</li>
            </ul>
            The scope of the Send/Receive operation can be limited as follows:
            <ul>
                <li><strong>Group</strong> sends all outbox articles associated with the same host as
                    the currently displayed group and receives articles of the currently displayed group.</li>
                <li><strong>Host</strong> sends all outbox articles associated with the host and receives
                    articles of all groups associated with the host of the currently displayed group.</li>
                <li><strong>All</strong> sends all outbox articles and receives articles of all groups.</li>
            </ul>
        </li>
        <li><strong>Filter</strong>
            <ul>
                <li><strong>All Threads</strong> displays all threads.</li>
                <li><strong>Watched</strong> displays only threads where the original article and/or
                    at least one of its direct or indirect follow-up articles is watched.</li>
                <li><strong>Unread</strong> displays only threads where the original article and/or
                    at least one of its direct or indirect follow-up articles is unread.</li>
                <li><strong>Watched &amp; Unread</strong> displays only threads where the original article
                    and/or at least one of its direct or indirect follow-up articles is watched <strong>
                        and</strong> unread.</li>
                <li><strong>Interesting</strong> displays only threads where the original article is
                    unread and/or at least one of its direct or indirect follow-up articles is watched
                    <strong>and</strong> unread. Unlike the watched &amp; unread filter, this option
                    ensures that new threads are shown to the user at least once.</li>
            </ul>
            If you'd like to read all articles that are posted in a group, you probably want
            to leave the <strong>Unread</strong> filter on most of the time. If you only like
            to follow a few select threads in a group, the <strong>Interesting</strong> option
            is probably the most useful. This filter assumes that you immediately watch each
            article you find interesting. Once you have read the original article of a thread
            without watching any of the thread's articles, the whole thread is deemed uninteresting
            and is no longer shown after the tree is refreshed.</li>
        <li><strong>Tools, Options...</strong> opens a dialog where hosts and groups can be
            added and removed. Initially, the tree contains a sample host and group. Their settings
            may serve as examples for additional hosts and groups. The meaning of the following
            host settings might not be obvious:
            <ul>
                <li><strong>Account Name</strong>: The account name for a server that requires log on
                    (must be left empty for public servers like e.g. news.mozilla.org).</li>
                <li><strong>Password</strong>: The password for a server that requires log on. Both
                    account name and password are stored in encrypted form.</li>
            </ul>
            Possibly non-obvious group settings:
            <ul>
                <li><strong>New Inbound Articles Receive Limit</strong>: The maximum number of new articles
                    for which information is received during each Send/Receive operation. Only new articles
                    count toward this limit. In any event, the full content is received for all incomplete
                    watched articles that are already present on the device (the ones having a torn
                    icon with an arrow). This setting comes into play during the very first Send/Receive
                    operation for a group and when Send/Receive is executed rarely.</li>
                <li><strong>Cached Inbound Articles Limit</strong>: The maximum number of inbound articles
                    that are held in the local cache. At application startup, if the total number of
                    excess articles of all groups is larger than 500, the oldest articles are deleted
                    from the cache such that the number of articles in all groups drops back to their
                    respective limits. Due to technical reasons, articles are only ever deleted from
                    groups that do not contain any unread articles.</li>
            </ul>
        </li>
    </ul>
</body>
</html>
